The HW design shall implement the HW safety requirements, with each element inheriting the highest
ASIL from the hardware safety requirements that are allocated to it. It is possible to lower the ASIL of a particular
element based upon the ASIL decomposition rules outline in ISO 26262, vol 9, clause 5. If sub-elements with different
ASIL exist within the main element then the highest ASIL is applied, unless the rules for coexistence, outlined in ISO
26262, vol 9, clause 6 are met.
In order to develop a hardware design safety and non safety requirements have to be complied with.
In this subphase both types of requirements are handled within the one development process.
The safety requirements shall be traced down to the level of the HW component, it is not necessary
to trace safety requirements and assign ASIL to hardware parts.
In order to avoid failures resulting from high complexity the hardware architectural design shall
exhibit properties such as modularity, simplicity and will be captured at adequate levels of granularity.
There are various properties of good modular HW design that are applicable
to items of different ASIL. However it should be noted that these techniques are intended to be
applied in combination and not separately.
Hierarchical design is recommended for Items of items of all ASIL
level
Precisely defined interfaces of safety-related hardware components is highly recommended for
Items of all ASIL level
Avoidance of unnecessary complex interfaces is recommended for Items of items of all ASIL
level
Avoidance of unnecessarily complex hardware components is recommended for Items of items of all
ASIL level
Ensure the ease of maintainability (service) is highly recommended for Items of ASIL C or D and
recommended for items of ASIL A or B
Ensure the ease of testability (which Includes testability during development and operation) is
highly recommended for Items of ASIL C or D and recommended for items of ASIL A
This information is a summary of the information taken from ISO 26262 vol 5, clause 7.4.1 Table 1 -
Properties of modular hardware design
When developing the detailed HW design in order to avoid common faults lessons learned from
previous experience should be applied and robust design principles considered.
Non-functional causes of failure for HW components and parts should be considered during
architectural design, such as temperature , vibration, water, dust, EMI, cross talk interference etc.
The HW parts to be used in the design shall comply with the specification of the environmental and
operational limits.
|